Method and apparatus for managing medical data

ABSTRACT

Provided are a method and apparatus for managing medical data. The method includes sensing an error event of a medical diagnosis device; obtaining image data by capturing images of a user input of the medical diagnosis device with respect to a first period of time associated with a time that the error event is sensed; obtaining log data corresponding to the image data, from a console device for controlling the medical diagnosis device; and transmitting the image data and the log data to an external server.

CROSS-REFERENCE TO RELATED PATENT APPLICATION

This application claims priority from Korean Patent Application No.10-2013-0072705, filed on Jun. 24, 2013, in the Korean IntellectualProperty Office, the disclosure of which is incorporated herein in itsentirety by reference.

BACKGROUND

1. Field

Exemplary embodiments relate to a method and apparatus for obtaining,managing, and transmitting medical data.

2. Description of the Related Art

A medical diagnosis system includes a large number of parts andcomponents for processing clinical information and diagnosing an object.As such, a user who manipulates a medical diagnosis system needshigh-level skills and knowledge.

If a user makes an error when manipulating a medical diagnosis system ora hardware/software problem inside the system exists, an error may begenerated during the operation of the medical diagnosis system. In otherwords, the operation of a medical diagnosis system may be interrupted orthe function of the system may temporarily deteriorate due to anunexpected problem.

Typically, in order to solve the above problem, log information storedin a console device of a medical diagnosis system is analyzed, or adebugging process using a debugging board is performed.

SUMMARY

Exemplary embodiments provide a method and apparatus for obtaining,managing, and transmitting medical data.

Exemplary embodiments may also provide a computer-readable recordingmedium having recorded thereon a computer program for executing themethod.

According to an aspect of an exemplary embodiment, there is provided amethod of managing medical data, performed by a medical data managementapparatus, the method including sensing an error event of a medicaldiagnosis device; obtaining image data by capturing images of a userinput unit of the medical diagnosis device with respect to a firstperiod of time associated with a time that the error event is sensed;obtaining log data corresponding to the image data, from a consoledevice for controlling the medical diagnosis device; and transmittingthe image data and the log data to an external server.

The obtaining of the image data may include capturing images of the userinput unit of the medical diagnosis device; and extracting imagescorresponding to the first period of time, from the captured images.

The obtaining of the log data may include transmitting information aboutthe first period of time to the console device; and receiving log datamatched to the first period of time, from the console device.

The image data and the log data may correspond to each other based onthe first period of time.

The method may further include obtaining image data corresponding to asecond period of time after the error event is sensed, from the imagesof the user input unit; obtaining log data corresponding to the secondperiod of time, from the console device; and transmitting the image datacorresponding to the second period of time and the log datacorresponding to the second period of time, to the external server.

The method may further include receiving a further transmission requestfrom the external server; further obtaining image data and log datacorresponding to a period of time according to the further transmissionrequest; and transmitting the further obtained image data and thefurther obtained log data to the external server.

The method may further include obtaining sound data of an operating roomwhere the medical diagnosis device is located, with respect to the firstperiod of time, and the transmitting may include transmitting the imagedata, the log data, and the sound data.

The sensing may include receiving an error event notification signalfrom the medical diagnosis device.

The sensing may include executing at least one of a pattern recognitionalgorithm, a gesture recognition algorithm, and a color detectionalgorithm on the images of the user input unit.

The transmitting may include transmitting information about one of thealgorithms, the executing of which results in the error event beingsensed.

The log data may include at least one of a history of using the consoledevice, user information of the console device, software information ofthe console device, setup information of the console device, systeminformation of the console device, and hospital information about ahospital where the medical data management apparatus is located.

The method may further include obtaining room image data by capturingimages of inside an operating room where the medical diagnosis device islocated, with respect to the first period of time, and the transmittingmay include transmitting the image data, the log data, and the roomimage data.

The method may further include setting an area for displaying the imagedata on a display unit; and providing the image data on the set area.

The image data may be obtained by an image capturing unit shielded fromthe medical diagnosis device.

The image data may be obtained by at least one of an ultra-high-speedcamera, a wide-viewing-angle camera, and a high-definition (HD) camera.

According to an aspect of another exemplary embodiment, there isprovided a medical data management apparatus including an imagecapturing unit for capturing images of a user input unit of a medicaldiagnosis device; an event sensing unit for sensing an error event ofthe medical diagnosis device; an image data management unit forobtaining image data by capturing images of the user input unit of themedical diagnosis device with respect to a first period of timeassociated with a time that the error event is sensed; a log datamanagement unit for obtaining log data corresponding to the image data,from a console device for controlling the medical diagnosis device; anda communication unit for transmitting the image data and the log data toan external server.

According to an aspect of another exemplary embodiment, there isprovided a non-transitory computer-readable recording medium havingrecorded thereon a computer program for executing the above method.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other features and advantages will become more apparent bydescribing in detail exemplary embodiments with reference to theattached drawings in which:

FIG. 1 is a schematic diagram showing correlations between a medicaldata management apparatus, a medical diagnosis device, a console device,and an external server, according to an exemplary embodiment;

FIG. 2 is a block diagram of a medical data management apparatusaccording to an exemplary embodiment;

FIG. 3 is a flowchart of a method of managing medical data, according toan exemplary embodiment;

FIG. 4 is a flowchart of a method of managing medical data, according toan exemplary embodiment;

FIG. 5 is a flowchart of a method of managing medical data in a medicaldiagnosis system, according to an exemplary embodiment;

FIG. 6 is a flowchart of a method of managing medical data, according toan exemplary embodiment;

FIG. 7 is a flowchart of a method of managing medical data, according toan exemplary embodiment;

FIG. 8 is a flowchart of a method of managing medical data, according toan exemplary embodiment;

FIG. 9 is a schematic diagram showing an example of managing medicaldata of a computed tomography (CT) diagnosis system, according to anexemplary embodiment;

FIG. 10 is a schematic diagram showing an example of managing medicaldata of an X-ray diagnosis system, according to an exemplary embodiment;

FIG. 11 is a schematic diagram showing an example of managing medicaldata of a magnetic resonance imaging (MRI) diagnosis system, accordingto an exemplary embodiment; and

FIG. 12 is a schematic diagram showing an example of managing medicaldata of an ultrasound diagnosis system, according to an exemplaryembodiment.

DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENTS

All terms including descriptive or technical terms which are used hereinshould be construed as having meanings that are known to one of ordinaryskill in the art. However, the terms may have different meaningsaccording to an intention of one of ordinary skill in the art, precedentcases, or the appearance of new technologies. Also, some terms may bearbitrarily selected by the applicant, and in this case, the meaning ofthe selected terms will be described in detail in the detaileddescription. Thus, the terms used herein have to be defined based on themeaning of the terms together with the description throughout thespecification.

Also, when a part “includes” or “comprises” an element, unless there isa particular description contrary thereto, the part can further includeother elements, not excluding the other elements. In the followingdescription, terms such as “unit” may be embodied as, but not limitedto, software or a hardware component, such as a field programmable gatearray (FPGA) or an application specific integrated circuit (ASIC).However, a unit may advantageously be configured to reside on anaddressable storage medium and configured to execute one or moreprocessors. Thus, a unit may include, by way of example, components,such as software components, object-oriented software components, classcomponents and task components, processes, functions, attributes,procedures, subroutines, segments of program code, drivers, firmware,microcode, circuitry, data, databases, data structures, tables, arrays,and variables. The functionality provided for in the components andunits may be combined into fewer components and units or furtherseparated into additional components and units.

Throughout the specification, an “image” may mean multi-dimensional dataincluding discrete image elements (e.g., pixels of a two-dimensional(2D) image and voxels of a three-dimensional (3D) image). For example,the image may include a medical image of an object which is obtained byusing an X-ray diagnosis system, a computed tomography (CT) diagnosissystem, a magnetic resonance imaging (MRI) diagnosis system, anultrasound diagnosis system, or another medical diagnosis system.

Also, throughout the specification, an “object” may include a human, ananimal, or a part of a human or animal. For example, the object mayinclude organs such as liver, heart, womb, brain, breast, abdomen, orthe like, or a blood vessel. Also, the object may include a phantom. Thephantom means a material having a volume that is very close to a densityand effective atomic number of an organism, and may include a spherephantom having a characteristic similar to a physical body.

Throughout the specification, a “user” may be, but is not limitedthereto, a medical expert including a doctor, a nurse, a medicallaboratory technologist, a medial image expert, a radiologist, and atechnician who repairs a medical apparatus.

Exemplary embodiments will now be described more fully with reference tothe accompanying drawings. The exemplary embodiments may, however, beembodied in many different forms and should not be construed as beinglimited to the exemplary embodiments set forth herein; rather, theseexemplary embodiments are provided so that this disclosure will bethorough and complete, and will fully convey the inventive concept tothose of ordinary skill in the art. In the following description,well-known functions or constructions are not described in detail sincethey would obscure the exemplary embodiments with unnecessary detail.Throughout the specification, like reference numerals in the drawingsdenote like elements.

As used herein, the term “and/or” includes any and all combinations ofone or more of the associated listed items. Expressions such as “atleast one of,” when preceding a list of elements, modify the entire listof elements and do not modify the individual elements of the list.

FIG. 1 is a schematic diagram showing correlations between a medicaldata management apparatus 100, a medical diagnosis device 10, a consoledevice 20, and an external server 200, according to an exemplaryembodiment. In FIG. 1, the medical data management apparatus 100 may beconnected to the medical diagnosis device 10, the console device 20, andthe external server 200. The medical diagnosis device 10, the consoledevice 20, and the medical data management apparatus 100 may beconnected to each other so as to form a medical diagnosis system 5.

The medical diagnosis device 10 may refer to a device for performingmedical diagnosis on an object. A user of the medical diagnosis device10 may control various components of the medical diagnosis device 10 bymanipulating a user input unit included in the medical diagnosis device10. The medical diagnosis device 10 may diagnose an object and maygenerate medical images. Also, the medical diagnosis device 10 maydisplay and output the generated medical images.

The medical diagnosis device 10 may include at least one of an MRIdiagnosis device, an X-ray diagnosis device, a CT diagnosis device, andan ultrasound diagnosis device. However, the above-mentioned diagnosisdevices are merely examples, and the medical diagnosis device 10 mayinclude diagnosis devices according to various modalities as well as theabove diagnosis devices.

The console device 20 may refer to a device for controlling and managingthe medical diagnosis device 10. The console device 20 may receive andanalyze system information of the medical diagnosis device 10, and maymonitor whether the medical diagnosis device 10 operates without anerror. Also, the console device 20 may obtain and store the systeminformation of the medical diagnosis device 10.

The console device 20 may be separate from the medical diagnosis device10 and may be located in a console room. A user of the console device 20may monitor and manage the medical diagnosis device 10 by manipulatingthe console device 20 in the console room.

The medical data management apparatus 100 obtains and manages medicaldata. The “medical data” may refer to data obtained by the medical datamanagement apparatus 100, and may include image data and log data. Theimage data and the log data will be described in detail below.

The medical data management apparatus 100 may obtain the image data fromthe above-described medical diagnosis device 10, and may obtain the logdata from the console device 20. Also, the medical data managementapparatus 100 may communicate with and may transmit the image data andthe log data to the external server 200. The medical data managementapparatus 100 may be connected to the external server 200 and theconsole device 20 via a network 30 by wire or wirelessly.

The “image data” may refer to images of the user input unit of themedical diagnosis device 10. In other words, the medical data managementapparatus 100 may capture images of the user input unit of the medicaldiagnosis device 10, and may obtain the captured images of the userinput unit as the image data.

The “log data” may refer to the system information of the medicaldiagnosis device 10. In other words, the medical data managementapparatus 100 may receive the system information obtained by the consoledevice 20 from the medical diagnosis device 10, and may manage thesystem information as the log data. The log data may include backup datafor system restoration when the medical diagnosis device 10malfunctions.

The external server 200 is connected to the medical data managementapparatus 100 and controls the medical diagnosis system 5. The externalserver 200 may analyze the medical data received from the medical datamanagement apparatus 100, i.e., the image data and the log data, and maycontrol the medical diagnosis device 10, the console device 20, and themedical data management apparatus 100.

For example, the external server 200 may perform an operation forcorrecting a malfunction of the medical diagnosis device 10, byanalyzing the log data of the medical diagnosis device 10. The externalserver 200 may include a service center server or a management centerserver of the medical diagnosis system 5.

FIG. 2 is a block diagram of the medical data management apparatus 100according to an exemplary embodiment. In other words, the medical datamanagement apparatus 100 may further include general components inaddition to those illustrated in FIG. 2, or may not include some of thecomponents illustrated in FIG. 2. Accordingly, the medical datamanagement apparatus 100 is not limited to the illustration anddescription of FIG. 2.

The medical data management apparatus 100 may include an event sensingunit 110 (e.g., an event sensor), an image capturing unit 120 (e.g., animage capturer), an image data management unit 130 (e.g., an image datamanager), a log data management unit 140 (e.g., a log data manager), amemory 150, a communication unit 160 (e.g., a communicator), a userinput unit 170 (e.g., a user input), a display unit 180 (e.g., adisplay), and a control unit 190 (e.g., a controller). The components ofthe medical data management apparatus 100 illustrated in FIG. 2 may beconnected to each other and may exchange data via a system bus 105. Eachof the components will now be described in detail.

The event sensing unit 110 senses an error event of the medicaldiagnosis device 10. In other words, the event sensing unit 110 mayobtain information about an error of the medical diagnosis device 10.The “error event” may refer to an event where an unexpected result isgenerated in the medical diagnosis device 10 due to a malfunction or asystem error.

For example, an operation of the medical diagnosis device 10 may beinterrupted due to an incorrect manipulation by the user. Alternatively,the medical diagnosis device 10 may not normally operate due to afailure or a crash of hardware or software. As another example, some orall functions of the medical diagnosis device 10 may be interrupted dueto a power supply or circuit error. In addition to the above-describedexamples, the “error event” may refer to all unexpected resultsgenerated in the medical diagnosis device 10.

As such, the event sensing unit 110 may sense an error event by usingvarious methods. For example, the event sensing unit 110 may receive anerror event notification signal from the medical diagnosis device 10.The error event notification signal may be a signal generated by themedical diagnosis device 10 when an error event is generated.

As another example, the event sensing unit 110 may sense whether anerror event is generated in the medical diagnosis device 10, bycyclically exchanging check data with the medical diagnosis device 10.In other words, if check data is not received from the medical diagnosisdevice 10, the event sensing unit 110 may recognize that an error eventis generated in the medical diagnosis device 10.

As another example, the event sensing unit 110 may sense an error eventby using a software method using various algorithms. In other words, theevent sensing unit 110 may obtain captured images of a user input unitof the medical diagnosis device 10 or captured images of an operatingroom where the medical diagnosis device 10 is located, and may apply oneor more algorithms to the obtained images. The event sensing unit 110may use various types of algorithms such as a pattern recognitionalgorithm, a gesture recognition algorithm, and a color detectionalgorithm.

In more detail, the event sensing unit 110 may detect an unexpectedpattern that is different from a predetermined pattern, on the capturedimages of the user input unit of the medical diagnosis device 10.Likewise, the event sensing unit 110 may detect an abnormal gesture oroperation performed with respect to the captured images of the userinput unit. Lastly, the event sensing unit 110 may sense generation ofan error event based on color variations on the images.

As another example, the event sensing unit 110 may sense generation ofan error event according to a user input received by the user input unit170. In other words, a user may interrupt an operation of the medicaldiagnosis device 10 or the medical data management apparatus 100according to a necessity. As such, the event sensing unit 110 mayreceive a user input for a system interrupt via the user input unit 170,and may recognize that an error event is generated, based on the userinput.

As described above, the event sensing unit 110 may sense an error eventactively, or passively by using a user input. Also, in addition to theabove-described examples, the event sensing unit 110 may sense an errorevent by using other various methods.

The image capturing unit 120 captures images of the user input unit ofthe medical diagnosis device 10. The image capturing unit 120 maycapture images of the medical diagnosis device 10 by using an imagingelement such as a camera. The image capturing unit 120 may includevarious types of imaging elements such as an ultra-high-speed camera, awide-viewing-angle camera, and a high-definition (HD) camera. Also, theimage capturing unit 120 may include a plurality of imaging elements.

The image capturing unit 120 may continuously monitor a user'smanipulation on the medical diagnosis device 10 by capturing images ofthe user input unit of the medical diagnosis device 10. The medicaldiagnosis device 10 may include one or more elements for receiving froma user an input for manipulating the medical diagnosis device 10. Forexample, the medical diagnosis device 10 may include various inputelements, e.g., a keyboard, a keypad, a mouse, a touch pad, a touchpanel, a touch screen, knob buttons, a jog switch, and a track ball, asthe user input unit.

As such, the image capturing unit 120 may be located near the user inputunit of the medical diagnosis device 10, and may capture images of theuser input unit. Examples wherein images of the user input unit of themedical diagnosis device 10 are captured according to various types ofmodalities will be described below with reference to FIGS. 9 through 12.

The image capturing unit 120 may capture images of the operating roomwhere the medical diagnosis device 10 is located. In other words, theimage capturing unit 120 may capture images of inside the operating roomand thus may generate room image data. If images of the user input unitare not easily captured due to motion of a user or a body part of theuser, the medical data management apparatus 100 may additionally use thecaptured images of the inside of the operating room.

Also, the image capturing unit 120 may capture images of an object inthe operating room. In other words, the image capturing unit 120 may belocated near a location where the medical diagnosis device 10 diagnosesan object, e.g., a diagnosis table, a cradle, or a diagnosis chair inthe operating room, and may capture images of the object during medicaldiagnosis. Then, the image capturing unit 120 may generate object imagedata including the captured images of the object.

The image capturing unit 120 may store the captured images of the userinput unit of the medical diagnosis device 10, the captured images ofthe operating room, or the captured images of the object in the memory150. The image capturing unit 120 may store the captured images in thememory 150 together with time information about times when the imagesare captured.

Also, the image capturing unit 120 may be shielded from the medicaldiagnosis device 10 in the operating room. In other words, the medicaldiagnosis device 10 such as an MRI diagnosis device or a CT diagnosisdevice irradiates a magnetic field or an X-ray. As such, the imagecapturing unit 120 may be located in the operating room while beingshielded from a magnetic field, a radio frequency (RF) signal, or anX-ray generated by the medical diagnosis device 10.

The image data management unit 130 obtains and manages some or all ofimage data including the images captured by the image capturing unit120. In other words, the image data management unit 130 may manage thecaptured images of the user input unit of the medical diagnosis device10 or the captured images of the operating room.

In more detail, the image data management unit 130 may extract the imagedata corresponding to a certain period of time of the image datacaptured by the image capturing unit 120 and stored in the memory 150.The period of time may refer to a certain period of time before and/orafter the event sensing unit 110 senses the error event. For example,the period of time may be a period of time from 5 minutes before theerror event is generated, till 10 minutes after the error event isgenerated. The period of time may directly precede, overlap with, orcome directly after the error event.

Also, the image data management unit 130 may further obtain the imagedata corresponding to a certain period of time according to a furthertransmission request received from the external server 200. In otherwords, if a request for the image data corresponding to a 10 minute timeperiod before the error event is generated is received from the externalserver 200, the image data management unit 130 may obtain the image datacorresponding to the above period of time, from the memory 150.

The log data management unit 140 obtains and manages log data from theconsole device 20. In other words, the log data management unit 140 mayreceive the log data including system information of the medicaldiagnosis device 10, from the console device 20, and may store the logdata in the memory 150.

Also, the log data management unit 140 may obtain the log datacorresponding to a certain period of time. The log data management unit140 may transmit information about the certain period of time t0 theconsole device 20, and may receive the log data matched to the period oftime, from the console device 20.

Alternatively, the log data management unit 140 may obtain some or allof the log data stored in the memory 150. In other words, the log datamanagement unit 140 may extract the log data corresponding to a certainperiod of time, from the log data stored in the memory 150.

Furthermore, the log data management unit 140 may further obtain the logdata corresponding to a certain period of time according to the furthertransmission request received from the external server 200. In otherwords, the log data management unit 140 may obtain the log datacorresponding to a certain period of time before and/or after the errorevent is sensed.

The log data may include at least one of a history of using the consoledevice 20, user information about a user who is logged in the consoledevice 20, software information about software installed in the consoledevice 20, hardware/software setup information of the console device 20,system information of the console device 20, and hospital informationabout a hospital where the medical data management apparatus 100 islocated.

The memory 150 may store data and information input/output to themedical data management apparatus 100. For example, the memory 150 maystore the image data captured by the image capturing unit 120, and maystore the log data received by the log data management unit 140 from theconsole device 20. Also, the memory 150 may store various types ofprogram data or algorithm data executable by the medical data managementapparatus 100.

The memory 150 may include at least one of a flash memory type storagemedium, a hard disk type storage medium, a multimedia card micro typestorage medium, a card-type memory (e.g., a security digital (SD) orextreme digital (XD) memory), a random access memory (RAM), a staticrandom access memory (SRAM), a read-only memory (SRAM), an electricallyerasable programmable read-only memory (EEPROM), a programmableread-only memory (PROM), a magnetic memory, a magnetic disk, and anoptical disk. Also, the medical data management apparatus 100 mayoperate a web storage or a cloud server, which performs the functions ofthe memory 150 on the internet.

The communication unit 160 is connected to the network 30 by wire orwirelessly and communicates with an external device or server. Thecommunication unit 160 may exchange data with a hospital serverconnected via a picture archiving and communication system (PACS), theexternal server 200, the medical diagnosis device 10, and the consoledevice 20. Also, the communication unit 160 may perform datacommunications according to the digital imaging and communications inmedicine (DICOM) standard.

The communication unit 160 may transmit and receive the image data andthe log data, or may receive a data request signal or a device controlcommand, via the network 30. Also, the communication unit 160 maytransmit and receive medical images captured by a device other than themedical diagnosis device 10.

Also, the communication unit 160 may receive a result of diagnosing theobject from the medical diagnosis device 10 as scan data, that is, dataabout medical images. The communication unit 160 may receive the scandata from the medical diagnosis device 10, and may transmit the scandata to the external server 200 in addition to the image data and thelog data.

As another example, the communication unit 160 may transmit to theexternal server 200 information about a method of sensing generation ofthe error event by the event sensing unit 110. In other words, if theevent sensing unit 110 senses the error event by receiving an errorevent notification signal or by applying an algorithm to the image data,information about each method may be transmitted to the external server200. As such, the external server 200 may check how the medical datamanagement apparatus 100 has sensed the error event.

The communication unit 160 may include one or more components forenabling communications via the network 30, e.g., a short-distancecommunication module, a wire communication module, and a mobilecommunication module.

The short-distance communication module refers to a module forshort-distance communications within a certain distance. Ashort-distance communication technology according to an exemplaryembodiment may include, but is not limited to, wireless local areanetwork (WLAN), wireless fidelity (Wi-Fi), Bluetooth, ZigBee, Wi-Fidirect (WFD), ultra wideband (UWB), infrared data association (IrDA),Bluetooth low energy (BLE), or near field communication (NFC).

The wire communication module refers to a module for communicationsusing an electrical signal or an optical signal. A wire communicationtechnology according to an exemplary embodiment may include, forexample, a pair cable, a coaxial cable, an optical fiber cable, or anEthernet cable.

The mobile communication module transmits and receives a wireless signalto and from at least one of a base station, an external terminal, and aserver in a mobile communication network. Here, the wireless signal mayinclude various types of data according to transmission and reception ofa voice call signal, a video call signal, or a text/multimedia message.

The user input unit 170 refers to an element for allowing a user (e.g.,a sonographer) to input data for controlling the medical data managementapparatus 100. For example, the user input unit 170 may include, but isnot limited to, a keyboard, a keypad, a mouse, a dome switch, a trackball, a touch pad (e.g., a capacitive overlay type, a resistive overlaytype, an infrared beam type, a surface acoustic wave type, an integralstrain gauge type, or a piezoelectric type), a jog wheel, or a jogswitch. Particularly, if a touch pad forms a layer structure togetherwith a display panel, the layer structure may be referred to as a touchscreen.

The user input unit 170 may detect a proximity touch as well as a realtouch. The user input unit 170 may sense a touch input (e.g., a touch &hold, a tap, a double tap, or a flick) on an image output by the displayunit 180. Also, the user input unit 170 may sense a drag input from apoint where a touch input is sensed. Furthermore, the user input unit170 may sense a multi-touch input (e.g., a pinch) on at least twopoints.

The user input unit 170 may receive a user input for setting an area fordisplaying the image data on the display unit 180.

The display unit 180 displays and outputs information processed by themedical data management apparatus 100. For example, the display unit 180may output a plurality of image data captured by the image capturingunit 120. The display unit 180 may display and output the image data onthe area set by the user.

If the display unit 180 and a touchpad form a touch screen in a layerstructure, the display unit 180 may be used as an input apparatus aswell as an output apparatus. The display unit 180 may include at leastone of a liquid crystal display (LCD), a thin film transistor LCD (TFTLCD), an organic light-emitting diode (OLED), a flexible display, athree-dimensional (3D) display, and an electrophoretic display. Themedical data management apparatus 100 may include two or more displayunits 180.

The control unit 190 controls all operations of the medical datamanagement apparatus 100. In other words, the control unit 190 maycontrol the image capturing unit 120 to store captured images in thememory 150, or may control the image data management unit 130 and thelog data management unit 140 to extract data stored in the memory 150.Alternatively, the control unit 190 may control the communication unit160 to exchange data by performing communications via the network 30.

Although not shown in FIG. 2, the medical data management apparatus 100may further include a sound data management unit (not shown). The sounddata management unit may record sound generated in the operating room,and may store the recorded sound as sound data in the memory 150. Likethe image data management unit 130 and the log data management unit 140,the sound data management unit may extract sound data corresponding to acertain period of time. The communication unit 160 according to anexemplary embodiment may transmit the sound data to the external server200 in addition to the image data and the log data.

FIG. 3 is a flowchart of a method of managing medical data, according toan exemplary embodiment. The method of FIG. 3 includes operationsperformed by the components included in the medical data managementapparatus 100 described above in relation to FIGS. 1 and 2. Accordingly,although not described below, the descriptions provided above inrelation to FIGS. 1 and 2 are also applied to the method of FIG. 3.

In operation 310, the medical data management apparatus 100 senses anerror event of the medical diagnosis device 10. In other words, themedical data management apparatus 100 may sense generation of anunexpected result due to a malfunction of the medical diagnosis device10.

As described above in relation to FIG. 2, the medical data managementapparatus 100 may sense generation of an error event by receiving anerror event notification signal from the medical diagnosis device 10, orby analyzing image data.

In operation 320, the medical data management apparatus 100 obtains theimage data corresponding to a certain period of time. In other words,the medical data management apparatus 100 captures and stores images ofa user input unit of the medical diagnosis device 10 by using the imagecapturing unit 120. In operation 320, the medical data managementapparatus 100 may obtain the image data corresponding to a period oftime determined in relation to generation of the error event.

The medical data management apparatus 100 may obtain the image datacorresponding to a certain period of time before the error event isgenerated. In other words, the medical data management apparatus 100 mayextract the image data corresponding to a certain period of time beforethe error event is generated, from the accumulatively stored image data.

For example, the medical data management apparatus 100 may extract theimage data corresponding to a 5 minute time period before the errorevent is generated. The period of time of the image data obtained by themedical data management apparatus 100 may be a predetermined period oftime, and may be adjusted according to a user input.

In operation 330, the medical data management apparatus 100 obtains logdata corresponding to the image data. In other words, the medical datamanagement apparatus 100 obtains the log data corresponding to theperiod of time of the image data obtained in operation 320.

The medical data management apparatus 100 may transmit information aboutthe period of time of the image data to the console device 20, and mayreceive the log data matched to the period of time, from the consoledevice 20.

In operations 320 and 330, the medical data management apparatus 100 mayobtain the image data and the log data matched to each other withrespect to the same period of time. The matched image data and the logdata may be synchronized with each other based on information about theperiod of time.

In operation 340, the medical data management apparatus 100 transmitsthe image data and the log data to the external server 200. In otherwords, the medical data management apparatus 100 may transmit medicaldata obtained in operations 320 and 330 (i.e., the image data and thelog data) to the external server 200.

The medical data management apparatus 100 may transmit the medical datato the external server 200, and may receive feedback information fromthe external server 200 including a service center server. As such, themedical data management apparatus 100 may not perform a debuggingprocess on the medical diagnosis device 10. In other words, thedebugging process may cause an overload of the medical diagnosis device10 and the console device 20 and thus may reduce a processing speed, andthe medical data management apparatus 100 may solve the above problem.

In more detail, the external server 200 that has received the medicaldata may analyze the image data as well as the log data. In other words,by solving a systematic problem while checking whether a user'smanipulation is correct, the external server 200 may easily check aproblem of the error event generated in the medical diagnosis device 10and the console device 20.

FIG. 4 is a flowchart of a method of managing medical data, according toanother exemplary embodiment. In FIG. 4, the exemplary embodimentdescribed above in relation to FIG. 3 is described in more detail.

In operation 410, the medical data management apparatus 100 capturesimages of a user input unit of the medical diagnosis device 10. Themedical data management apparatus 100 may capture images of the userinput unit of the medical diagnosis device 10 by using at least oneimage capturing unit 120 and may obtain images corresponding to anoperation of a user who manipulates the medical diagnosis device 10.

According to another exemplary embodiment, the medical data managementapparatus 100 may capture images of inside an operating room where themedical diagnosis device 10 is located. Also, the medical datamanagement apparatus 100 may capture images of an object located in theoperating room.

As described above in relation to FIG. 2, the medical data managementapparatus 100 may store the images captured in operation 410, as imagedata in the memory 150. The medical data management apparatus 100 maystore time information about times when the images are captured, to bematched to the image data.

In operation 420, the medical data management apparatus 100 senses anerror event. Operation 420 is similar to operation 310 of FIG. 3 andthus is not described in detail here.

In operation 430, the medical data management apparatus 100 extracts theimage data corresponding to a certain period of time, from the imagescaptured in operation 410. The medical data management apparatus 100 mayextract the image data corresponding to a certain period of time beforeand/or after the error event is sensed in operation 420.

In operation 440, the medical data management apparatus 100 transmitsinformation about the period of time of the extracted image data to theconsole device 20. Then, in operation 450, the medical data managementapparatus 100 receives from the console device 20 log data matched tothe period of time indicated by the information transmitted to theconsole device 20.

In other words, in operations 440 and 450, the medical data managementapparatus 100 may receive the log data corresponding to the image dataextracted with respect to the certain period of time. The medical datamanagement apparatus 100 may obtain the image data and the log datawhich correspond to each other with respect to the same period of time.

In operation 460, the medical data management apparatus 100 transmitsthe image data and the log data to the external server 200. A detaileddescription thereof is similarly provided above in relation to operation340 of FIG. 3.

FIG. 5 is a flowchart of a method of managing medical data in a medicaldiagnosis system, according to an exemplary embodiment. In FIG. 5,detailed descriptions provided above in relation to FIGS. 3 and 4 willnot be repeated here.

In operation 510, the medical data management apparatus 100 capturesimages of a user input unit of the medical diagnosis device 10, andgenerates image data. The medical data management apparatus 100 maystore the image data to be matched to time information.

In operation 520, an error event is generated in the medical diagnosisdevice 10. In other words, the medical diagnosis device 10 may providean unexpected result due to an incorrect manipulation by the user or asystem error. The error event is described above in detail in relationto FIG. 2.

In operation 530, the medical data management apparatus 100 senses theerror event of the medical diagnosis device 10. For example, the medicaldata management apparatus 100 may sense the error event by receiving anerror event notification signal from the medical diagnosis device 10, orby analyzing the image data generated in operation 510.

In operation 540, the medical data management apparatus 100 extracts theimage data corresponding to a certain period of time. The medical datamanagement apparatus 100 may extract the image data corresponding to acertain period of time before and/or after the error event is generated.

In operation 550, the medical data management apparatus 100 may transmitto the console device 20 information about the period of time of theimage data extracted in operation 540. Then, in operation 560, themedical data management apparatus 100 may receive from the consoledevice 20 log data corresponding to the period of time indicated by theinformation transmitted in operation 550.

In operation 570, the medical data management apparatus 100 may transmitthe extracted image data and the received log data to the externalserver 200.

The medical data management apparatus 100 may obtain and transmit sounddata in addition to the image data and the log data. In other words,when the image data of the user input unit of the medical diagnosisdevice 10 is obtained in operation 510, the medical data managementapparatus 100 may obtain and store sound data by recording sound in anoperating room where the medical diagnosis device 10 is located.

Then, the medical data management apparatus 100 may extract sound datacorresponding to the period of time of the image data extracted inoperation 540, and may transmit the sound data to the external server200 together with the image data and the log data in operation 570.

FIG. 6 is a flowchart of a method of managing medical data, according toan exemplary embodiment. In FIG. 6, a certain period of time forobtaining image data and log data after the medical data managementapparatus 100 senses an error event is described.

In operation 610, the medical data management apparatus 100 obtainsimage data corresponding to a certain period of time after an errorevent is sensed. The medical data management apparatus 100 maypreviously determine the certain period of time according to a userinput. For example, the medical data management apparatus 100 maypreviously set a 5 minute time period after the error event is sensed,as the period of time for obtaining the image data.

If the error event is sensed, the medical data management apparatus 100may obtain and transmit the image data in real time. In other words, theimage data corresponding to a period of time before the error event issensed may be previously obtained. However, the image data correspondingto a period of time after the error event is sensed may not bepreviously obtained.

Accordingly, if the error event is sensed, the medical data managementapparatus 100 may obtain and transmit the image data in real time for apredetermined certain period of time.

In operation 620, the medical data management apparatus 100 obtains logdata corresponding to the certain period of time after the error eventis sensed. Like operation 610, in operation 620, the medical datamanagement apparatus 100 may obtain the log data in real time for apredetermined period of time after the error event is sensed.

In other words, the medical data management apparatus 100 may obtain andreceive the log data in real time from the console device 20.

In operation 630, the medical data management apparatus 100 transmitsthe image data and the log data to the external server 200. In otherwords, the medical data management apparatus 100 may transmit to theexternal server 200 medical data obtained in operations 610 and 620after the error event is sensed.

FIG. 7 is a flowchart of a method of managing medical data, according toan exemplary embodiment. In FIG. 7, communications between the medicaldata management apparatus 100 and the external server 200 are described.

In operation 710, the medical data management apparatus 100 transmitsimage data and log data to the external server 200. The medical datamanagement apparatus 100 may transmit to the external server 200 theimage data and the log data which correspond to each other with respectto a period of time before and/or an error event is sensed. As describedabove in relation to, for example, FIG. 2, the medical data managementapparatus 100 may also transmit sound data.

In operation 720, the external server 200 analyzes the received medicaldata. In other words, the external server 200 may analyze the imagedata, the log data, and the sound data so as to check a cause and typeof the error event generated in the medical diagnosis device 10.

In operations 730 and 735, the medical data management apparatus 100further transmits the medical data to the external server 200. In otherwords, unlike the medical data corresponding to a period of time beforethe error event is sensed, the medical data management apparatus 100 mayobtain and transmit the medical data in real time for a certain periodof time after the error event is generated.

The medical data management apparatus 100 may obtain and transmit themedical data in units of a certain period of time. In other words, forexample, the medical data management apparatus 100 may obtain themedical data for a 5 minute time period after the error event is sensed,in units of one minute, and may separately transmit the medical data tothe external server 200.

During operations 730 and 735, the external server 200 may continuouslyanalyze the medical data about the error event.

In operation 740, the medical data management apparatus 100 receives atransmission interruption request from the external server 200. In otherwords, the medical data management apparatus 100 may receive from theexternal server 200 a signal indicating that the error event has beencompletely analyzed, and a signal requesting to interrupt thetransmitting of the medical data.

As such, in operation 750, the medical data management apparatus 100interrupts the transmitting of the medical data. In other words, themedical data management apparatus 100 may interrupt the obtaining andtransmitting of data for a certain period of time after the error eventis generated.

In operation 760, the medical data management apparatus 100 receives afurther transmission request from the external server 200. In otherwords, in order to further analyze the error event, the external server200 may require the medical data corresponding to a period of timelonger than that of the medical data that has been transmitted from themedical data management apparatus 100 or may require data from anotherperiod of time.

As such, the medical data management apparatus 100 may receive from theexternal server 200 the further transmission request requesting tofurther transmit the medical data. Then, in operation 770, the medicaldata management apparatus 100 further obtains the medical data. In otherwords, the medical data management apparatus 100 may obtain the medicaldata corresponding to a period of time other than those of the medicaldata transmitted in operations 710, 730, and 735.

In operation 780, the medical data management apparatus 100 transmits tothe external server 200 the medical data further obtained in operation770. As such, the external server 200 may perform further operations foranalyzing a cause of the error event generated in the medical diagnosisdevice 10, and for solving the error event.

FIG. 8 is a flowchart of a method of managing medical data, according toan exemplary embodiment. FIG. 8 shows the method according to the flowof time. In FIG. 8, the descriptions provided above in relation to FIGS.3 through 7 will not repeated here.

In operation 810, the medical data management apparatus 100 senses anerror event at a point of time t0. Then, in operation 820, the medicaldata management apparatus 100 may obtain medical data corresponding to aperiod of time t1 to t0 that is a certain period of time before thepoint of time t0 when the error event is sensed, and may transmit themedical data to the external server 200.

Then, in operation 830, the medical data management apparatus 100 mayobtain the medical data corresponding to a period of time t0 to t2 thatis a certain period of time after the point of time t0 when the errorevent is sensed, and may transmit the medical data to the externalserver 200.

The medical data management apparatus 100 may obtain and transmit themedical data corresponding to the period of time t0 to t2, to theexternal server 200 in real time. In other words, unlike the medicaldata corresponding to the period of time t1 to t0, the medical datamanagement apparatus 100 may obtain and transmit the medical datacorresponding to the period of time t0 to t2, to the external server 200in real time.

As described above in relation to FIG. 7, the medical data managementapparatus 100 may obtain and transmit the medical data to the externalserver 200 in units of a certain period of time after the error event isgenerated.

In operation 840, the medical data management apparatus 100 receives atransmission interruption request from the external server 200. As such,the medical data management apparatus 100 may interrupt the obtainingand transmitting of the medical data.

In operation 850, the medical data management apparatus 100 receives afurther transmission request from the external server 200. In otherwords, the medical data management apparatus 100 may be requested by theexternal server 200 to further transmit the medical data required toanalyze the error event.

In operation 860, according to the further transmission request receivedin operation 850, the medical data management apparatus 100 obtains andtransmits the medical data corresponding to a period of time t3 to t1,to the external server 200. In other words, if the medical datacorresponding to the period of time t1 to t0 is not sufficient toanalyze and check the error event, according to a request from theexternal server 200, the medical data management apparatus 100 mayfurther manage data corresponding to a period of time before the errorevent is generated.

Likewise, in operation 870, the medical data management apparatus 100further obtains and transmits the medical data corresponding to a periodof time t2 to t4, to the external server 200. In other words, if thefurther transmission request is received at a point of time t4, themedical data management apparatus 100 may transmit the medical dataobtained and stored with respect to the period of time t2 to t4, to theexternal server 200.

Furthermore, until the transmission interruption request is received,the medical data management apparatus 100 may obtain and transmit themedical data corresponding to a period of time after the point of timet4, to the external server 200.

FIG. 9 is a schematic diagram showing an example of managing medicaldata of a CT diagnosis system, according to an exemplary embodiment. InFIG. 9, the medical data management apparatus 100 includes first throughfourth image capturing units 932, 934, 936, and 938 for capturing imagesof a plurality of user input units included in a CT diagnosis device910.

In other words, the medical data management apparatus 100 includes thefirst image capturing unit 932 for capturing images of a control panel922 attached to a gantry of the CT diagnosis device 910. Also, themedical data management apparatus 100 includes the second imagecapturing unit 934 for capturing images of table control buttons 924attached to a diagnosis table of the CT diagnosis device 910.

Likewise, the medical data management apparatus 100 includes the thirdimage capturing unit 936 and the fourth image capturing unit 938 forcapturing images of a touch panel 926 and a keyboard 928 for controllingthe CT diagnosis device 910.

Also, the medical data management apparatus 100 may further include afifth image capturing unit 950 for capturing images of inside theoperating room 900. The fifth image capturing unit 950 may generateimage data obtained by capturing images of inside of the while operatingroom 900, and thus may supplement the image data captured by the firstthrough fourth image capturing units 932, 934, 936, and 938.

In addition, the medical data management apparatus 100 may furtherinclude a sixth image capturing unit 990 for capturing images of anobject located in the operating room 900. The sixth image capturing unit990 may capture images of the object that is being diagnosed, and maygenerate object image data. The medical data management apparatus 100may transmit the object image data to the external server 200 togetherwith the image data and log data. In addition, another image capturingunit may be located internal to touch panel 926 or another computingdevice and capture screenshots of the touch panel or the computingdevice from a memory of the computing device.

FIG. 10 is a schematic diagram showing an example of managing medicaldata of an X-ray diagnosis system, according to an exemplary embodiment.In FIG. 10, the medical data management apparatus 100 includes firstthrough third image capturing units 1032, 1034, and 1036 for capturingimages of a plurality of user input units included in an X-ray diagnosisdevice 1010.

In other words, the medical data management apparatus 100 may includethe first image capturing unit 1032 for capturing images of a voltagecontrol unit 1022 of the X-ray diagnosis device 1010. Likewise, themedical data management apparatus 100 may include the second imagecapturing unit 1034 for capturing images of a system control unit 1024of the X-ray diagnosis device 1010, and the third image capturing unit1036 for capturing images of a keyboard 1026 of the X-ray diagnosisdevice 1010.

As described above in relation to FIG. 9, the medical data managementapparatus 100 of FIG. 10 may further include an image capturing unit(not shown) for capturing images of inside an operating room where theX-ray diagnosis device 1010 is located.

Also, similarly to FIG. 9, the medical data management apparatus 100 ofFIG. 10 may further include a fourth image capturing unit 1090 forcapturing images of an object located in the operating room.

FIG. 11 is a schematic diagram showing an example of managing medicaldata of an MRI diagnosis system, according to an exemplary embodiment.In FIG. 11, the medical data management apparatus 100 may include firstthrough third image capturing units 1132, 1134, and 1136 for capturingimages of user input units of an MRI diagnosis device 1110.

The medical data management apparatus 100 may include the first imagecapturing unit 1136 for capturing images of a bore control panel 1126 ofthe MRI diagnosis device 1110. Also, the medical data managementapparatus 100 may include the second image capturing unit 1134 forcapturing images of a touch screen 1124 of the MRI diagnosis device1110, and the third image capturing unit 1132 for capturing images of akeyboard 1122 of the MRI diagnosis device 1110.

Also, although not shown in FIG. 11, as described above in relation toFIGS. 9 and 10, the medical data management apparatus 100 may furtherinclude an image capturing unit for capturing images of an objectdiagnosed by the MRI diagnosis device 1110 in an operating room.

FIG. 12 is a schematic diagram showing an example of managing medicaldata of an ultrasound diagnosis system, according to an exemplaryembodiment. In FIG. 12, the medical data management apparatus 100 mayinclude first through fourth image capturing units 1232, 1234, 1236,1238, and 1240 for capturing images of user input units of an ultrasounddiagnosis device 1210.

The first through fourth image capturing units 1232, 1234, 1236, 1238,and 1240 may respectively capture images of a contrast medium injector1222, a probe connector 1224, a keyboard 1226, a probe holder 1228, anda foot switch 1230 of the ultrasound diagnosis device 1210.

Similarly to FIGS. 9 and 10, in FIGS. 11 and 12, the medical datamanagement apparatus 100 may further include an image capturing unit(not shown) for capturing images of an operating room where the MRIdiagnosis device 1110 or the ultrasound diagnosis device 1210 islocated.

As described above in relation to FIG. 2, the image capturing unitsillustrated in FIGS. 9 through 12 may be shielded from a magnetic field,an RF signal, or an X ray generated by a medical diagnosis device (e.g.,910, 1010, 1110, or 1210).

In FIGS. 9 through 12, examples of image capturing units of the medicaldata management apparatus 100 according to various modalities aredescribed. However, the above descriptions are merely examples and theprevious exemplary embodiments are not limited thereto.

Exemplary embodiments may be written as computer programs and may beimplemented in general-use digital computers that execute the programsusing a computer readable recording medium. Also, the data structureused in the exemplary embodiments described above may be recorded on acomputer readable recording medium via various elements. Examples of thecomputer readable recording medium include magnetic storage media (e.g.,ROM, floppy disks, hard disks, etc.), optical recording media (e.g.,CD-ROMs, or DVDs), etc.

As described above, since the medical data management apparatus 100obtains and transmits medical data, the external server 200 may managethe medical data for analyzing an error event of the medical diagnosisdevice 10. As such, a cause of the error event of the medical diagnosisdevice 10 may be efficiently checked. Also, a load for performing adebugging process using a debugging board may be reduced.

Also, since the medical data management apparatus 100 obtains andtransmits medical data for a designated period of time, trafficconsumption according to transmission of unnecessary data may bereduced.

Furthermore, since a user's manipulation is monitored and analyzed so asto give feedback on the incorrect manipulation by the user, apossibility of generating an error event may also be reduced.

While the exemplary embodiments have been particularly shown anddescribed with reference to drawings, it will be understood by one ofordinary skill in the art that various changes in form and details maybe made therein without departing from the spirit and scope of theinventive concept as defined by the following claims. The exemplaryembodiments should be considered in a descriptive sense only and not forpurposes of limitation. Therefore, the scope of the inventive concept isdefined not by the detailed description but by the following claims, andall differences within the scope will be construed as being included inthe inventive concept.

What is claimed is:
 1. A method of managing medical data, performed by amedical data management apparatus, the method comprising: sensing anerror event of a medical diagnosis device; obtaining image data bycapturing images of a user input of the medical diagnosis device withrespect to a first period of time before the error event is sensed;obtaining log data corresponding to the image data, from a consoledevice for controlling the medical diagnosis device; and transmittingthe image data and the log data to an external server.
 2. The method ofclaim 1, wherein the obtaining image data comprises: capturing images ofthe user input of the medical diagnosis device; and extracting imagescorresponding to the first period of time, from the captured images. 3.The method of claim 1, wherein the obtaining log data comprises:transmitting information about the first period of time to the consoledevice; and receiving log data matched to the first period of time, fromthe console device.
 4. The method of claim 1, wherein the image data andthe log data correspond to each other based on the first period of time.5. The method of claim 1, further comprising: obtaining image datacorresponding to a second period of time after the error event issensed, from the images of the user input; obtaining log datacorresponding to the second period of time, from the console device; andtransmitting the image data corresponding to the second period of timeand the log data corresponding to the second period of time, to theexternal server.
 6. The method of claim 1, further comprising: receivinga further transmission request from the external server; furtherobtaining image data and log data corresponding to a period of timeaccording to the further transmission request; and transmitting thefurther obtained image data and the further obtained second log data tothe external server.
 7. The method of claim 1, further comprisingobtaining sound data of an operating room where the medical diagnosisdevice is located, with respect to the first period of time, wherein thetransmitting comprises transmitting the image data, the log data, andthe sound data.
 8. The method of claim 1, wherein the sensing comprisesreceiving an error event notification signal from the medical diagnosisdevice.
 9. The method of claim 1, wherein the sensing comprisesexecuting at least one of a pattern recognition algorithm, a gesturerecognition algorithm, and a color detection algorithm on the images ofthe user input.
 10. The method of claim 9, wherein the transmittingcomprises transmitting information about one of the algorithms, theexecuting of which results in the error event being sensed.
 11. Themethod of claim 1, wherein the log data comprises at least one of ahistory of using the console device, user information of the consoledevice, software information of the console device, setup information ofthe console device, system information of the console device, andhospital information about a hospital where the medical data managementapparatus is located.
 12. The method of claim 1, further comprisingobtaining room image data by capturing images of inside an operatingroom where the medical diagnosis device is located, with respect to thefirst period of time, wherein the transmitting comprises transmittingthe image data, the log data, and the room image data.
 13. The method ofclaim 1, further comprising obtaining a result of diagnosing an objectas scan data with respect to the first period of time, wherein thetransmitting comprises transmitting the image data, the log data, andthe scan data.
 14. The method of claim 1, further comprising obtainingobject image data by capturing images of an object located in anoperating room, with respect to the first period of time, wherein thetransmitting comprises transmitting the image data, the log data, andthe object image data.
 15. The method of claim 1, further comprising:setting an area for displaying the image data on a display; andproviding the image data on the set area.
 16. The method of claim 1,wherein the image data is obtained by an image capturer shielded fromthe medical diagnosis device.
 17. The method of claim 1, wherein theimage data is obtained by at least one of an ultra-high-speed camera, awide-viewing-angle camera, and a high-definition (HD) camera.
 18. Amedical data management apparatus comprising: an image capturer which isconfigured to capture images of a user input of a medical diagnosisdevice; at least one processor which is configured to sense an errorevent of the medical diagnosis device, obtain image data by capturingimages of the user input of the medical diagnosis device with respect toa first period of time before the error event is sensed, and obtain logdata corresponding to the image data, from a console device forcontrolling the medical diagnosis device; and a communicator which isconfigured to transmit the image data and the log data to an externalserver.
 19. The medical data management apparatus of claim 18, whereinthe at least one processor extracts images corresponding to the firstperiod of time, from the images of the user input captured by the imagecapturer.
 20. The medical data management apparatus of claim 18, whereinthe at least one processor transmits information about the first periodof time to the console device, and receives log data matched to thefirst period of time, from the console device.
 21. The medical datamanagement apparatus of claim 18, wherein the image data and the logdata correspond to each other based on the first period of time.
 22. Themedical data management apparatus of claim 18, wherein the at least oneprocessor obtains image data corresponding to a second period of timeafter the error event is sensed, from the images of the user input, andobtains log data corresponding to the second period of time, from theconsole device, and wherein the communicator transmits the image datacorresponding to the second period of time and the log datacorresponding to the second period of time, to the external server. 23.The medical data management apparatus of claim 18, wherein thecommunicator receives a further transmission request from the externalserver, wherein the at least one processor obtains further image datacorresponding to a period of time according to the further transmissionrequest, and further log data corresponding to the period of timeaccording to the further transmission request, and wherein thecommunicator transmits the further obtained image data and the furtherobtained log data to the external server.
 24. The medical datamanagement apparatus of claim 18, wherein the at least one processor isfurther configured to obtain sound data of an operating room where themedical diagnosis device is located, with respect to the first period oftime, wherein the communicator transmits the image data, the log data,and the sound data.
 25. The medical data management apparatus of claim18, wherein the at least one processor receives an error eventnotification signal from the medical diagnosis device.
 26. The medicaldata management apparatus of claim 18, wherein the at least oneprocessor executes at least one of a pattern recognition algorithm, agesture recognition algorithm, and a color detection algorithm on theimages of the user input.
 27. The medical data management apparatus ofclaim 26, wherein the communicator transmits information about one ofthe algorithms, which has sensed the error event.
 28. The medical datamanagement apparatus of claim 18, wherein the log data comprises atleast one of a history of using the console device, user information ofthe console device, software information of the console device, setupinformation of the console device, system information of the consoledevice, and hospital information about a hospital where the medical datamanagement apparatus is located.
 29. The medical data managementapparatus of claim 18, wherein the image capturer captures images ofinside an operating room where the medical diagnosis device is located,wherein the at least one processor obtains room image data including theimages of inside the operating room captured with respect to the firstperiod of time, and wherein the communicator transmits the image data,the log data, and the room image data.
 30. The medical data managementapparatus of claim 18, wherein the communicator obtains a result ofdiagnosing an object as scan data with respect to the first period oftime, and transmits the image data, the log data, and the scan data. 31.The medical data management apparatus of claim 18, wherein the imagecapturer captures images of an object located in an operating room,wherein the at least one processor obtains object image data includingthe images of the object captured with respect to the first period oftime, and wherein the communicator transmits the image data, the logdata, and the object image data.
 32. The medical data managementapparatus of claim 18, further comprising: a display, wherein the atleast one processor is further configured to set an area for displayingthe image data on the display, and provide the image data on the setarea.
 33. The medical data management apparatus of claim 18, wherein theimage capturer obtains the image data while being shielded from themedical diagnosis device.
 34. The medical data management apparatus ofclaim 18, wherein the image capturer comprises at least one of anultra-high-speed camera, a wide-viewing-angle camera, and ahigh-definition (HD) camera.
 35. A non-transitory computer-readablerecording medium having recorded thereon a computer program forexecuting the method of claim
 1. 36. A method of managing medical data,performed by a medical data management apparatus, the method comprising:sensing an error event of a medical diagnosis device; obtaining imagedata by capturing images of a user input of the medical diagnosisdevice; obtaining log data from a console device for controlling themedical diagnosis device; and storing the image data and the log data tobe matched to each other with respect to a certain period of time.
 37. Amedical data management apparatus comprising: an image capturer which isconfigured to capture images of a user input of the medical diagnosisdevice; at least one processor which is configured to sense an errorevent of the medical diagnosis device, obtain image data including thecaptured images of the user input of the medical diagnosis device, andobtain log data from a console device for controlling the medicaldiagnosis device; and a memory which is configured to store the imagedata and the log data to be matched to each other with respect to acertain period of time.
 38. A medical diagnosis system comprising: amedical diagnosis device which is configured to diagnose an objectlocated in an operating room; a console device which is configured tocontrol the medical diagnosis device in a console room; and a medicaldata management apparatus, wherein the medical data managementapparatus: senses an error event of the medical diagnosis device;obtains image data by capturing images of a user input of the medicaldiagnosis device with respect to a first period of time before the errorevent is sensed; obtains log data corresponding to the image data, fromthe console device; and transmits the image data and the log data to anexternal server.